drm/vc4: Use runtime autosuspend to avoid thrashing V3D power state.
authorEric Anholt <eric@anholt.net>
Fri, 4 Nov 2016 22:58:38 +0000 (15:58 -0700)
committerpopcornmix <popcornmix@gmail.com>
Mon, 20 Feb 2017 20:31:42 +0000 (20:31 +0000)
commitd3f28cc2457435a42cc1244193d5ada900a7a6ad
treefcebb766e67a5bfe819e200223d125ee3085f576
parent1e63ff0c37e40816639806088f961208a4fed823
drm/vc4: Use runtime autosuspend to avoid thrashing V3D power state.

The pm_runtime_put() we were using immediately released power on the
device, which meant that we were generally turning the device off and
on once per frame.  In many profiles I've looked at, that added up to
about 1% of CPU time, but this could get worse in the case of frequent
rendering and readback (as may happen in X rendering).  By keeping the
device on until we've been idle for a couple of frames, we drop the
overhead of runtime PM down to sub-.1%.

Signed-off-by: Eric Anholt <eric@anholt.net>
(cherry picked from commit 3a62234680d86efa0239665ed8a0e908f1aef147)
drivers/gpu/drm/vc4/vc4_drv.c
drivers/gpu/drm/vc4/vc4_gem.c
drivers/gpu/drm/vc4/vc4_v3d.c